Skip to content

TAMES CaseMail endpoint#6988

Merged
ERosendo merged 36 commits intomainfrom
morgan/texas-casemail
Apr 10, 2026
Merged

TAMES CaseMail endpoint#6988
ERosendo merged 36 commits intomainfrom
morgan/texas-casemail

Conversation

@MorganBennetDev
Copy link
Copy Markdown
Contributor

Resolves #6685

Summary

Adds an endpoint to ingest TAMES CaseMail emails at /api/v4/scrapers/email/state/tx/tames/alert.

Awaiting completion of the email parser in #1757 to proceed.

Deployment

This PR should:

  • skip-deploy (skips everything below)
    • skip-web-deploy
    • skip-celery-deploy
    • skip-cronjob-deploy
    • skip-daemon-deploy

Awaiting completion of email parser
@MorganBennetDev MorganBennetDev moved this to In progress in Sprint (Web Team) Feb 18, 2026
@MorganBennetDev MorganBennetDev self-assigned this Feb 18, 2026
@MorganBennetDev MorganBennetDev changed the title feat(texas): Skeleton for case email endpoint TAMES CaseMail endpoint Feb 18, 2026
@MorganBennetDev MorganBennetDev moved this from In progress to Blocked in Sprint (Web Team) Feb 20, 2026
@MorganBennetDev MorganBennetDev moved this from Blocked to To Do in Sprint (Web Team) Mar 3, 2026
@MorganBennetDev MorganBennetDev moved this from To Do to In progress in Sprint (Web Team) Mar 4, 2026
@MorganBennetDev MorganBennetDev marked this pull request as ready for review March 4, 2026 22:28
@MorganBennetDev
Copy link
Copy Markdown
Contributor Author

This depends on JS#1812 and CL#6862 to be merged, but is otherwise complete

@MorganBennetDev MorganBennetDev moved this from In progress to To Do in Sprint (Web Team) Mar 4, 2026
@albertisfu albertisfu moved this from To Do to In progress in Sprint (Web Team) Mar 5, 2026
Copy link
Copy Markdown
Contributor

@albertisfu albertisfu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @MorganBennetDev, this looks good.

Just one small comment, and I think this will be ready.

Copy link
Copy Markdown
Contributor

@albertisfu albertisfu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @MorganBennetDev, this is ready to go. We'll wait to merge it so the required migration can be applied by the infra team alongside the other migrations we need for Texas.

@albertisfu albertisfu moved this from To Do to Blocked in Sprint (Web Team) Apr 1, 2026
@albertisfu
Copy link
Copy Markdown
Contributor

@MorganBennetDev could you solve merge conflicts in this PR when you have a moment please?

@MorganBennetDev
Copy link
Copy Markdown
Contributor Author

@albertisfu Resolved. Should be good to go again.

@ERosendo
Copy link
Copy Markdown
Contributor

Hi @MorganBennetDev, could you please take a look at the merge conflicts in this PR when you have a moment?

@MorganBennetDev
Copy link
Copy Markdown
Contributor Author

@ERosendo Merge conflicts resolved along with a failing test. Should be good to merge now.

@ERosendo ERosendo enabled auto-merge April 10, 2026 16:01
@ERosendo ERosendo merged commit d35f8d2 into main Apr 10, 2026
9 checks passed
@ERosendo ERosendo deleted the morgan/texas-casemail branch April 10, 2026 16:08
@github-project-automation github-project-automation bot moved this from Blocked to Done in Sprint (Web Team) Apr 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Implement an API endpoint to ingest Texas CaseMail notifications

4 participants